Memory error detection

ABSTRACT

Systems and methods are provided for detecting and correcting address errors in a memory system. In the memory system, a memory device generates an error-detection code based on an address transmitted via an address bus and transmits the error-detection code to a memory controller. The memory controller transmits an error indication to the memory device in response to the error-detection code. The error indication causes the memory device to remove the received address and prevent a memory operation

RELATED APPLICATION

This application is a continuation-in-part application of applicationSer. No. 12/035,022, Attorney Docket Number RA-468C1, entitled “Systemto Detect and Identify Errors in Control Information, Read Data and/orWrite Data,” by inventors Ian Shaeffer, Craig Hampel, Yuanlong Wang, andFred Ware, filed 21 Feb. 2008, which is a continuation of applicationSer. No. 11/436,284, Attorney Docket Number RA-468, entitled “System toDetect and Identify Errors in Control Information, Read Data and/orWrite Data,” by inventors Ian Shaeffer and Craig Hampel, filed 18 May2006.

BACKGROUND

The present disclosure relates generally to memory systems. Moreparticularly, the present disclosure relates to detection and correctionof errors within a memory system.

As the data transfer rate in computer systems becomes progressivelyfaster, modern memory systems are more prone to transmission errors.Noise, crosstalk, inter-symbol interference, among other factors, cansignificantly impair signal quality, especially as data rates approachmultiple Gbps.

BRIEF DESCRIPTION OF THE FIGURES

This disclosure is illustrated by way of example, and not by way oflimitation, in the accompanying drawings. Like reference numerals referto similar elements.

FIG. 1 illustrates an exemplary memory system which facilitates errordetection for both data and address, in accordance with one embodimentof the present invention.

FIG. 2A presents a block diagram illustrating the process of generatingEDC codes based on both data and address, in accordance with oneembodiment of the present invention.

FIG. 2B presents a block diagram illustrating the process of generatingEDC codes based on both data and address, in accordance with oneembodiment of the present invention.

FIG. 3 presents a flowchart illustrating the operation of a dynamicrandom-access memory (DRAM) which facilitates EDC for both address anddata, in accordance with one embodiment of the present invention.

FIG. 4 presents a flowchart illustrating the operation of a memorycontroller which facilitates EDC for both address and data, inaccordance with one embodiment of the present invention.

FIG. 5 presents an exemplary timing diagram illustrating the operationbetween a memory controller and a DRAM to facilitate address and dataEDC, in accordance with one embodiment of the present invention.

FIG. 6 presents an exemplary timing diagram illustrating the operationbetween a memory controller and a DRAM to facilitate address and dataEDC, in accordance with one embodiment of the present invention.

The following description is presented to enable any person skilled inthe art to make and use embodiments disclosed herein, and is provided inthe context of a particular application and its requirements. Variousmodifications to the disclosed embodiments will be readily apparent tothose skilled in the art, and the general principles defined herein maybe applied to other embodiments and applications without departing fromthe spirit and scope of the present disclosure. Thus, the presentdisclosure is not limited to the embodiments shown, but is to beaccorded the widest scope consistent with the disclosure.

DETAILED DESCRIPTION

In a memory system, address errors can be more detrimental than dataerrors, because a write operation with the wrong address can corruptpreviously stored data. Embodiments of the present invention provide amechanism for checking and correcting errors in both address and datatransmission between the memory controller and DRAM. The DRAM computesan error-detection code (EDC) based on the address and/or data receivedfrom the controller, and transmits this EDC code back to the controller.The controller then determines whether the EDC code is consistent withthe previously transmitted address and/or data. If an error is detected,and if the error corresponds to the address for a write operation, thecontroller can send an error indication to the DRAM, so that the DRAMcan cancel the erroneous write command. In this way, the memory systemcan ensure both error-resistant data and address transmission.

Embodiments of the present invention also provide various configurationsto optimize different characteristics of the memory system. For example,the DRAM can compute the address-based EDC code as soon as the addressis received, thereby reducing the amount of latency incurred to the datadue to buffering. The DRAM also subjects the received address (andoptionally the received data) to additional delays, so that there issufficient time for the controller to detect an error based the EDC codeand issue an error indication. The total delay incurred to the addressand optionally the data is sufficient such that the operationcorresponding to an erroneous address can be precluded from beingcompleted. This total delay may be more than the normal WRITE or READlatency. In further embodiments, the controller can withhold the datatransmission until it receives and confirms the EDC code for thecorresponding address, which reduces the amount of in-DRAM databuffering.

In the present disclosure, a “memory controller” or “controller” refersto a circuit, chip, or device on a computer's motherboard or CPU diewhich manages the flow of data going to and from the memory. A “DRAM”refers a dynamic random-access memory. Embodiments of the presentinvention are not limited to DRAM-specific applications. Theseembodiments can also be applied to various memory systems based ondynamic or static memories. The terms “data transmission” and “data”refer to the payload data transferred between the controller and DRAM.Although the address and command bits can also be broadly referred to asdata, the term “data” in this disclosure, unless specified otherwise,refers to the payload bits which are separate from address and commandbits. An “error indication” is a command or a signal transmitted by thecontroller to a DRAM, so the DRAM can prevent a memory operationcorresponding to an erroneously received address from being completed.An error indication can be a command including one or more bits,transmitted via or outside of the command bus. The error indication canalso be a separate signal transmitted via one or more separate pins.

FIG. 1 illustrates an exemplary memory system 100 which facilitateserror checking and correction for both data and address, in accordancewith one embodiment of the present invention. Memory system 100 includesa DRAM controller 110, a DRAM 140, a command bus 132, an address bus134, a data bus (DQ bus) 136, and an error-detection code (EDC) bus 138.DRAM controller 110 includes command generation circuitry 113, addressgeneration circuitry 112, write data circuitry 114, read data circuitry116, a write data buffer 122, an address buffer 124, a read/writeselector 120, and error detection circuitry 118. DRAM 140 includescommand/error handling circuitry 142, an address buffer 146, a databuffer 147, a read/write selector 148, and a cyclic-redundancy-check(CRC) code generator 150.

During operation, command generation circuitry 113 generates a memorycommand, e.g., a read or write command, and places the command oncommand bus 132. At approximately the same time, address generationcircuitry 112 places an address corresponding to the memory command onaddress bus 134. If the command is for a write operation, write datacircuitry 114 places the data for the write operation in buffer 122. Ingeneral, buffer 122 is used to delay the data transmission after thewrite command and address have been sent to DRAM 140, due to the writelatency present in DRAM 140, i.e., the delay between the time when DRAM140 receives the command and address and the time when DRAM 140 is readyto accept data on DQ bus 136. If command generation circuitry 113generates a read command, a certain amount of data buffering might alsobe necessary to accommodate the read latency in DRAM 140.

After command generation circuitry 113 places the command on command bus132, command/error handling circuitry 142 in DRAM 140 receives thetransmitted command. In addition, the corresponding address is receivedand placed in buffer 146. Typically, buffer 146 buffers the receivedaddress bits because the complete address (e.g., bank address, rowaddress, and/or column address) may be transmitted over multiple clockcycles. Furthermore, buffer 146 ensures that the address informationremains available until DRAM 140 is ready to receive the write data.

Subsequently, after a certain delay (e.g., the write latency), thecorresponding data is received and buffered in buffer 147. Buffer 147buffers the received data so that buffer 147 can be later frozen or thedata can be discarded if DRAM controller 110 identifies an error in thetransmitted address. At a given time, the data present on DQ bus 136might not correspond to the address and/or command present on addressbus 134 and command bus 132, due to the pipelined operation of memorysystem 100.

The received address is first buffered by buffer 146 and then sent toCRC generator 150. In addition, the write data is sent to CRC generator150 via read/write selector 148. Read/write selector 148 is controlledby command/error handling circuitry 142 based on the received command.If the command indicates a read operation, read/write selector 148allows the outgoing data from the DRAM core to be sent to CRC generator150. If the command indicates a write operation (which is the case inthe current example), read/write selector 148 allows the write data tobe sent to CRC generator 150.

CRC generator 150 produces a CRC code based on both the address andwrite data. The CRC code is then transmitted via EDC bus 138 to DRAMcontroller 110. CRC generator 150 can concatenate the address with thedata to produce an input to the CRC computation. Other methods ofgenerating the CRC code based on both the address and data are alsopossible.

In this example, the EDC code generated by DRAM 140 is a CRC code. A CRCcode (or “CRC”) is an error-detecting code. Its computation resembles along division operation in which the quotient is discarded and theremainder becomes the result, with the distinction that the arithmeticused is the carry-less arithmetic of a finite field. The length of theremainder is less than or equal to the length of the divisor, whichtherefore determines how long the result can be. The definition of aparticular CRC specifies the divisor to be used. The CRC code generatedby CRC generation circuitry 150 can be based on the polynomialexpression X⁸+X²+X¹+1. In general, a respective EDC pin in EDC bus 138is used to carry the CRC code for the data transmitted on a number(e.g., eight) of DQ pins within DQ bus 136. There is one EDC pin forevery eight DQ pins, and the CRC code is transmitted via the EDC pinover eight data-clock periods, which correspond to eight data bitstransmitted over each DQ pin. That is, an eight-bit serial CRC code istransmitted over one EDC pin for 64 bits of data transmitted via eightDQ pins over eight data-clock cycles. Other EDC code schemes can also beused.

After DRAM controller 110 receives the CRC code, error detectioncircuitry 118 compares the CRC code with a local CRC code generatedbased on the buffered write data and address. Alternatively, errordetection circuitry 118 can checksum the buffered write data and addressconcatenated with the same CRC polynomial, and determines whether thechecksum result is zero. The write address is buffered in buffer 124 tocompensate for the delay between the time when the address istransmitted to DRAM 140 and the time when the CRC code is received andchecked at DRAM controller 110. Error detection circuitry 118 also takesas input the write or read data which corresponds to the CRC receivedfrom DRAM 140. Controller 110 maintains a set of state information tokeep track of the address and data (which may be for different memoryoperations) corresponding to the received CRC code. The stateinformation may be maintained by command generation circuitry 113. Uponreceiving the CRC code from DRAM 140, command generation circuitry 113determines whether the received CRC code corresponds to write or readdata, and sends a signal (denoted as “R/W”) to read/write selector 120.In response, read/write selector 120 selects the appropriate data (i.e.,write or read) to send to error detection circuitry 118.

If the received CRC code is consistent with the selected data andaddress, controller 110 does not send any error indication to DRAM 140.As a result, after a predetermined period, DRAM 140 can automaticallyproceed with the write operation based on the address stored in buffer146 and the corresponding write data.

Instead of transmitting an explicit error indication, controller 110 cantransmit an explicit “commit” indication to DRAM 140 when the CRC codeis consistent with the buffered data and address. This commit indicationcan be a command transmitted via or outside the command bus, or a signaltransmitted over one or more separate pins. In response to the commitindication, DRAM 140 can proceed to commit the memory operation to theDRAM core. If the CRC code is inconsistent with the buffered data andaddress at controller 110, no commit indication is sent. As a result,after a certain time-out period, DRAM 140 can prevent the memoryoperation from being completed if no commit indication is received.

If error detection circuitry 118 detects an error based on the receivedCRC code, it can cause command generation circuitry 113 to generate andtransmit an error indication to DRAM 140 via command bus 132. (The errorindication can also be transmitted via one or more dedicated pinsseparate from command bus 132.) In response, command/error handlingcircuitry 142 can cause buffer 146 to remove the stored addresscorresponding to the error, and optionally cause buffer 147 to removethe corresponding write data. Buffer 146 can include a number oflatches, and removing the stored address involves resetting theselatches. In addition, in response to the error indication, command/errorhandling circuitry 142 can prevent the memory operation corresponding tothe erroneously received address from being completed. For example, acommit of the memory operation to the memory core can be deliberatelydelayed sufficiently long using buffer 146 and/or buffer 147, such thatcontroller 110 has time to detect errors and, if appropriate, abort theassociated command. Subsequently, command generation circuitry 113re-issues the corresponding memory commands. It is possible that the CRCcode which identifies an error is derived from a write address and readdata. In this case, the controller does not need to determine the sourceof the error (i.e., whether the error was incurred to the write addressor read data) and can simply re-transmit all the transactions to whichthe erroneous CRC code corresponds.

Depending on the pipelined operations, DRAM 140 may discard a number of“in-flight” transactions (including command, address, and optionallydata) received after the memory operation corresponding to the erroneousaddress. This approach can avoid read-after-write and write-after-writeconflicts that could otherwise occur and also corrupt data in some way.In general, command/error handling circuitry 142 can discard the memorycommand associated with the error (or commands associated with the errorif the error corresponds to more than one command due to pipelining).Command/error handling circuitry 142 can further discard anysubsequently received command that can present a hazardous conflict withthe command in error (for example, a read-after-write orwrite-after-read situation). Alternatively, command/error handlingcircuitry 142 can discard all the commands it has received and bufferedafter the erroneous command and before the first retransmitted command.

The CRC code could be generated based on address and data which belongto two or more memory operations due to the pipelined operation betweencontroller 110 and DRAM 140. As a result, command generation circuitry113 may need to re-issue two memory commands. Furthermore, if a writecommand is re-issued, the write data previously buffered in buffer 122is sent to DRAM 140 again, in response to a signal from error detectioncircuitry 118 (denoted by an arrow from error detection circuitry 118 tobuffer 122).

To minimize the delay between address transmission and the receiving ofCRC code at controller 110, DRAM 140 can be configured to compute theCRC code as soon as the address is received, without first buffering thereceived address (denoted by a dotted arrow from the address flow to CRCgenerator 150). The CRC code can also be generated based on the addressand data bits for the same memory operation. This configuration mayinvolve additional buffering of the address, because the datatransmission typically occurs after the address transmission. It is,nevertheless, not required to generate the CRC code based on the addressand data corresponding to the same memory transaction, so long as boththe controller and DRAM have an agreement on how to map a CRC code tothe appropriate memory transaction(s).

Controller 110 can withhold the write data transmission until a CRC codecorresponding to the address for the same operation is received andconfirmed. This configuration may require additional buffering of thewrite data within controller 110. This buffering can be accomplished bybuffer 122.

The example described above is described in the context of a writeoperation. In the case of a read operation, read/write selector 148allows the data read from the DRAM core to be sent to CRC generator 150.In controller 110, read/write selector 120 also allows the received readdata to be sent to error detection circuitry 118. If an error isdetected for a read command, only the read command and the correspondingaddress is re-transmitted to DRAM 140, since errors in a read command,address, or data do not potentially result in irrecoverable datacorruption in DRAM 140.

As noted above, there is usually write and read latency within DRAM 140.To improve system efficiency and utilization, the transfer of addressesand data between controller 110 and DRAM 140 is typically pipelined.That is, at a given moment, the bits carried on address bus 134 and thebits carried on data bus 136 may correspond to different operations.Hence, CRC generator 150 can generate CRC codes based on address anddata belonging to different operations.

FIG. 2A presents a block diagram illustrating the process of generatinga CRC code with pipelined write operations, in accordance with oneembodiment of the present invention. This example shows a number ofwrite operations, the address and data of which (denoted as “A” and “D”respectively) are indexed by a subscript which indicates their order.These write operations are pipelined in such a way that the write datafor a prior operation can be present on the DQ bus when the address forthe current operation is on the address bus. In FIG. 2A, the write datais assumed to lag behind the address by k memory commands. For example,when address A_(n) is on the address bus, write data D_(n−k) is on theDQ bus. As a result, the CRC generator within the DRAM can generate aCRC code, CRC_(n), based on A_(n) and D_(n−k). k can be any integer,such as 0, 1, 2, 3, etc.

The value of k represent the about of lag of data behind thecorresponding address. In addition to the write or read latency inherentin the DRAM, k can also include artificially injected buffering delay tothe data to accommodate the time required to generate the CRC code,process the CRC code at the controller, and to issue an error indicationby the controller. This way, the buffered memory command can be abortedbefore the data is committed to the DRAM core.

When k is zero, the data on the DQ bus is substantially aligned with theaddress on the address bus and they correspond to the same memoryoperation. However, in such a configuration, the DRAM may need toprovide sufficient in-DRAM buffering for the write data to accommodatethe write latency. One advantage of having the data and address aligned(i.e., corresponding to the same memory command) for generating the CRCcode is that when an error is detected, the DRAM only needs to abortand/or re-issue the memory command corresponding to that error. When thedata and address are not aligned (i.e., k is greater than zero), thecontroller might not be able to determine whether the error in the CRCcorresponds to the data or address. As a result, the DRAM might need toabort multiple commands corresponding to the address and data,respectively. The controller might also need to re-issue these commands.

It is possible that sometimes the DQ bus is not always busy, and a givenCRC code might be generated based only on an address, whereas the dataportion of the input for the CRC is of a null value. In this case, theDRAM only needs to abort the command corresponding to the address if anerror is detected in the CRC code.

In the example in FIG. 2B, a CRC code, CRC_(n), is generated based onA_(n), D_(n−k), and D_(n−k+1). In other words, a particular CRC isgenerated based on not only the address and data present on the addressbus and DQ bus, but also on the data corresponding to the previousmemory command. This method can allow the controller to determinewhether an error in CRC_(n) is caused by an error in A_(n), D_(n−k), orD_(n−k+1). For example, if CRC_(n) is in error, but CRC_(n+1) andCRC_(n−1) are both correct, then A_(n)is in error. If CRC_(n) andCRC_(n−1) are both in error but CRC_(n+1) and CRC_(n−1) are correct,then it is possible that D_(n−k) and/or A_(n) are in error.

Other methods are possible to allow the controller to determine whethera CRC error is caused by an address error or data error. For example,the DRAM can generate CRC codes for the data and address separately, andtransmit both CRC codes to the controller.

The description below provides further explanation of the operations ofthe DRAM and controller, and exemplary timing diagrams of differentembodiments.

FIG. 3 presents a flowchart illustrating the operation of a DRAM whichfacilitates EDC for both address and data, in accordance with oneembodiment of the present invention. In this example, the DRAM firstreceives a command and the corresponding address (operation 302). TheDRAM can also receive write data if the command is for a writeoperation, wherein the write data may or may not correspond to the writecommand and address due to pipelined operations. Subsequently, the DRAMcomputes a CRC code based on the received address and optionally thedata (operation 304). The data could be write data (incoming) or readdata (outgoing). The DRAM then transmits the CRC code to the memorycontroller (operation 306).

Next, the DRAM determines whether it has received an error indicationfrom the controller before a given time (referred to as “retire time”)(operation 308). If the DRAM does not receive the error indicationbefore the retire time, the DRAM proceeds with normal operations, suchas write, read, active, refresh, and other register-related operations(operation 310). If an error indication is received, the DRAM purges theaddress corresponding to the error from the address buffer andoptionally one or more pending commands following the command in error(operation 314). Subsequently, the DRAM receives a re-issued write orread command, the address, and optionally data (if the re-issued commandis for a write operation) from the controller (operation 316). The DRAMthen proceeds to handle the re-issued command (operation 304).

FIG. 4 presents a flowchart illustrating the operation of a memorycontroller which facilitates EDC for both address and data, inaccordance with one embodiment of the present invention. In thisexample, the memory controller first transmits a command and address,and optionally write data to the DRAM (operation 402). Subsequently, thecontroller receives from the DRAM a CRC code based on the transmittedaddress and optionally write or read data (operation 404). Thecontroller then performs the checksum computation on the bufferedaddress (and optionally buffered data) concatenated with the receivedCRC code (operation 406). A correct CRC code would produce zero as thechecksum result. Alternatively, the controller can generate its own CRCcode and compare it with the received CRC code. The address andoptionally the data and command used to generate the CRC code should bethe same as the ones used to check the CRC code. However, they do notneed to be for the same memory transaction.

Next, the controller determines whether received CRC code is correct(operation 408). If the CRC codes is correct, the controller proceeds tothe next memory operation (operation 410). If the CRC code is incorrect,the controller further determines whether the address associated withthe error corresponds to a read or write operation (operation 412).

If the address error corresponds to a write operation, the controllerissues an error indication to the DRAM (operation 414). This errorindication notifies the DRAM that it should discard or abort thecommands for the previously stored erroneous address, and, if thecorresponding write data has already been transmitted to the DRAM,discard the buffered write data as well. Subsequently, the controllerre-issues the write command corresponding to the erroneous address(operation 416). Optionally, if the CRC code from the DRAM is based onaddress and data belonging to two different memory operations, thecontroller can re-issue the write or read command corresponding to thedata portion (as opposed to the address portion) associated with theerror (operation 420).

In a further embodiment, instead of sending an explicit error indicationto the DRAM when the CRC is incorrect, the controller can send anexplicit commit indication when the CRC is correct. This commitindication allows the DRAM to proceed with the buffered command andcomplete the memory operation. Correspondingly, if the CRC is incorrect,the controller does not transmit the commit indication, and the DRAMdiscards the command in error (and optionally additional pendingcommands received after the command in error) after a predeterminedtime-out period.

If the erroneous data portion is for a previously issued write command,it is not necessary for the controller to issue an error indication tothe DRAM to discard the erroneous data, because the erroneous data willstill be written to the correct address and will not corrupt good datastored elsewhere. The controller only needs to re-issue the writecommand to place the correct data in the same address. To illustratethis situation more clearly, take the example in FIG. 2. Suppose addressA_(n) and data D_(n−k) are for two separate write commands. Also,suppose CRC_(n) indicates an error. The controller then assumes thatboth write commands respectively corresponding to A_(n) and D_(n−k) haderroneous transmission. However, the controller only needs to issue anerror indication for the write operation corresponding to A_(n), so thatthe DRAM can purge the stored erroneous address A_(n)′. The controllerdoes not have to issue an error indication for the write operationcorresponding to D_(n−k), because even if the erroneous data is writtento the DRAM core, it can be corrected by a re-issued write command,since there is no address error associated with D_(n−k). This is basedon the assumption that the controller does not issue a read commandimmediately following the erroneous write command to the same address.The controller can ensure this does not happen by comparing the addressof pending read operations with the erroneous write operation andholding the read operations until the correct write data is committed.Alternatively, the controller can return the correct read data based onthe data buffered within the controller, without addressing the DRAM atall.

Now, with reference back to operation 412 in FIG. 4, if the controllerdetermines that the address associated with the error corresponds to aread operation, the controller re-issues the read command correspondingto the erroneous address (operation 418). The controller can optionallyre-issue the write or read command corresponding to the data portionassociated with the error (operation 420). Subsequently, the controllerproceeds to receive the next CRC code from the DRAM (operation 404).

Note that although the above example is directed to erroneous read andwrite operations, the same method can be applied to other types ofoperations, such as activate, refresh, and other register-relatedoperations. In general, this method can be applied to any memoryoperation that involves transmission of an address.

FIG. 5 presents an exemplary timing diagram illustrating the operationbetween a memory controller and a DRAM to facilitate address and dataEDC, in accordance with one embodiment of the present invention. In thisexample, the clock and inverted clock signals are denoted as “clk” and “clk” respectively. Each clock cycle is denoted as T_(i). The command canbe transmitted at every rising edge of clk, and address can betransmitted at every rising edge of clk and clk. In other words, thedata rate of address transmission is twice that of command transmission.The data clock used in this example is twice as fast as the clock forcommand and address transmission. Here, the data clock and inverted dataclock signals are denoted as “wclk” and “ wclk” respectively. The databits on the DQ bus and the CRC bits on the EDC bus are transmitted atevery rising edge of wclk and wclk. Hence, the data rate of DQ and EDCis four times the data rate of the command bus and twice the data rateof the address bus.

In this example, at clock cycle T₀, the controller issues a writecommand WR₀, and places the corresponding addresses, AD₀₁ and AD₀₂, onthe address bus. Assume that the DRAM has a write latency of two clockcycles (i.e., WL=2). The corresponding write data burst 512 is placed onthe DQ bus at clock cycle T₂. Assume that each write data burst is eightbits long. Hence, data burst 512 occupies clock cycles T₂ and T₃.Meanwhile, at T₃, the controller issues the next write command WR₁ andthe corresponding addresses AD₁₁ and AD₁₂. AD₁₁ and AD₁₂ are received bythe DRAM at approximately the same time as data burst 512 (which is thewrite data for WR₀). The DRAM concatenates AD₁₁ and AD₁₂ with data burst512, generates a CRC code 522, and places CRC code 522 on the EDC bus atT₄.

While the controller receives CRC code 522, the controller continues toissue the next write command, WR₂, and its corresponding address AD₂₁and AD₂₂ at T₅. In addition, at T₅, the controller places data burst514, which is the write data for WR₁, on the DQ bus.

After receiving CRC code 522, the controller detects an error (indicatedby a star), and issues an error indication 515 to the DRAM at T₇. Errorindication 515 corresponds to the write command WR₁ and allows the DRAMto discard the erroneously received addresses AD₁₁ and AD₁₂. Subsequentto error indication 515, the controller re-issues WR₀ and WR₁ at T₈ andT₁₀, respectively. The controller does not need to issue an errorindication for WR₀, if the address of WR₀ has been received correctly bythe DRAM and there is no potential data hazard between WR₀ and WR₁. Inresponse to error indication 515, the DRAM can discard the bufferedaddress AD₀₁ and AD₀₂, and optionally buffered data burst 512.

Meanwhile, at T₇, the controller places data burst 516, which is thewrite data corresponding to WR₂, on the DQ bus. On the DRAM side, afterreceiving data burst 514, the DRAM concatenates AD₂₁ and AD₂₂ with databurst 514 and generates CRC code 524. Subsequent to data burst 514, thecontroller transmits data burst 516, which is the write data for WR₂. AtT₁₀, the controller transmits data burst 518, which is the write datafor the re-issued WR₀.

Because data bursts 514 and 516 are received at the DRAM back-to-back,the DRAM also generates CRC code 526 based on AD₀₁, AD₀₂, and data burst516. AD₀₁ and AD₀₂ at T₈ correspond to the re-issued WR₀. Since thecontroller does not find any error in CRC codes 524 and 526 (indicatedby a check mark), the controller does not perform any additionaloperations with respect to these CRC codes.

In this example, there are seven clock cycles between the time when theaddress for WR₀ (AD₀₁ and AD₀₂) is placed on the address bus and thetime when error indication 515 is issued. Correspondingly, theseaddresses are buffered in the DRAM for seven clock cycles in order forthe DRAM to abort them in response to an error indication. This bufferdelay is longer than the DRAM's normal write latency, which is two clockcycles. This buffering can be provided by buffer 146 in the systemillustrated in FIG. 1. If the time required for the DRAM to compute theCRC and for the controller to check the CRC and issue an errorindication is deterministic, the amount of buffering for the receivedaddress can also be determined. Furthermore, the DRAM can include amechanism that determines this total latency required for the CRC checkand configure the buffer automatically during a start-up sequence, suchthat the received addresses are buffered sufficiently long to allow theCRC check and error notification.

FIG. 6 presents an exemplary timing diagram illustrating the operationbetween a memory controller and a DRAM to facilitate address and dataEDC, in accordance with one embodiment of the present invention. In thisexample, the controller is configured to transmit the write data afterthe corresponding write address is confirmed to have been receivedsuccessfully at the DRAM. The write latency in this example is assumedto be three clock cycles (i.e., WL=3).

As illustrated in FIG. 6, at T₀, the controller issues the first writecommand WR₀ and the corresponding addresses, AD₀₁ and AD₀₂. Based onAD₀₁ and AD₀₂, the DRAM generates CRC code 622. Subsequently, thecontroller determines that CRC code 622 is error-free, and transmitsdata burst 614, which is the write data for WR₀. Similarly, the DRAMgenerates CRC code 624 based on AD₁₁ and AD₁₂. Upon receiving andconfirming CRC code 624, the controller transmits data burst 616, whichis the write data corresponding to WR₁.

Data burst 614 is transmitted at T₃. Since data burst 614 lasts two fullclock cycles (i.e., from T₃ to T₅), which coincide with the transmissionof WR₂, AD₂₁, and AD₂₂, the DRAM can first buffer AD₂₁ and AD₂₂ and thenconcatenate them with data burst 614 to produce CRC code 626. Uponreceiving and confirming CRC code 626, the controller proceeds totransmit data burst 618, which is the write data corresponding to WR₂.

In the example above, the DRAM generates a CRC code based on thereceived address as soon as the address is received, provided there isno data being received on the DQ bus. The controller would withhold thewrite data transmission until the CRC code corresponding to the writeaddress is received and confirmed. However, when the DRAM receivesaddresses and data at the same time (for example, data burst 614, AD₂₁,and AD₂₂), the DRAM can first buffer the address and then generate theCRC code based on both the address and received data.

Although the description uses read and write operations as examples, themethods disclosed herein are not limited to these operations. Ingeneral, the present address error-detection mechanisms are applicablewith any memory operation that involves an address transmission.

The components of the address error detection mechanism described abovecan include any collection of computing components and devices operatingtogether. These components can also be components or subsystems in alarger computer system or network. Components of an address errordetection mechanism can also be coupled among any number of components(not shown), for example, buses, controllers, memory devices, and datainput/output (I/O) devices, in any number of combinations. Many of thesesystem components may be situated on a common printed circuit board orintegrated circuit, or may be integrated in a system that includesseveral printed circuit boards or ICs that are coupled together in asystem, for example, using connector and socket interfaces such as thoseemployed by personal computer motherboards and dual inline memorymodules (“DIMM”). In other examples, complete systems may be integratedin a single package housing using a system in package (“SIP”) type ofapproach. Integrated circuit devices may be stacked on top of oneanother and utilize wire bond connections to effectuate communicationbetween devices or may be integrated on a single planar substrate in thepackage housing.

Further, functions of an address error detection mechanism can bedistributed among any number/combination of other processor-basedcomponents. The address error detection mechanism described above can beapplied in, for example, various DRAM systems. As examples, the DRAMmemory systems can include DDR systems like DDR SDRAM, as well as DDR2SDRAM, DDR3 SDRAM, and other DDR SDRAM variants, such as Graphics DDR(“GDDR”) and further generations of these memory technologies, includingGDDR2, GDDR3, GDDR4, and GDDR5, but are not limited to these memorysystems.

Aspects of the address error detection mechanisms described herein maybe implemented as functionality programmed into any of a variety ofcircuitry, including programmable logic devices (PLDs), such as fieldprogrammable gate arrays (FPGAs), programmable array logic (PAL)devices, electrically programmable logic and memory devices, andstandard cell-based devices, as well as application specific integratedcircuits (ASICs). The underlying device technologies may be provided ina variety of component types, e.g., metal-oxide semiconductorfield-effect transistor (MOSFET) technologies like complementarymetal-oxide semiconductor (CMOS), bipolar technologies likeemitter-coupled logic (ECL), polymer technologies (e.g.,silicon-conjugated polymer and metal-conjugated polymer-metalstructures), mixed analog and digital, etc.

The foregoing descriptions of embodiments described herein have beenpresented only for purposes of illustration and description. They arenot intended to be exhaustive or to limit the embodiments to the formsdisclosed. Accordingly, many modifications and variations will beapparent to practitioners skilled in the art.

Moreover, some components are shown directly connected to one another,while others are shown connected via intermediate components. In eachinstance the method of interconnection, or ‘coupling,’ establishes somedesired electrical communication between two or more circuit nodes, orterminals. Such coupling may often be accomplished using a number ofcircuit configurations, as will be understood by those of skill in theart. Therefore, the spirit and scope of the appended claims should notbe limited to the foregoing description. Only those claims specificallyreciting “means for” or “step for” should be construed in the mannerrequired under the sixth paragraph of 35 U.S.C. §112.

1. A memory device, comprising: address-receiving circuitry to receivean address for a memory operation; address-storage circuitry to storethe received address for the memory operation; indication-receivingcircuitry to receive an error indication which indicates an error in thereceived address for the memory operation; and error-handling circuitryto prevent the memory operation from being completed in response to thereceived error indication.
 2. The memory device of claim 1, furthercomprising a buffering mechanism to buffer the received address for anamount of time that is at least sufficient for the indication-receivingcircuitry to receive the error indication.
 3. The memory device of claim2, wherein the time for which the received address is buffered is longerthan a write latency or read latency inherent to the memory device. 4.The memory device of claim 1, wherein while preventing the memoryoperation from being completed, the error-handling circuitry aborts areceived command corresponding to the memory operation and writing overthe received address with a correct address.
 5. The memory device ofclaim 1, wherein while preventing the memory operation from beingcompleted, the error-handling circuitry discards one or more memorycommands associated with the error.
 6. The memory device of claim 5,wherein while preventing the memory operation from being completed, theerror-handling circuitry further discards a memory command receivedsubsequent to the command associated with the error, wherein thesubsequently received command can present a hazardous conflict with thecommand associated with the error.
 7. The memory device of claim 1,further comprising: error-management circuitry to generate anerror-detection code based on the received address for the memoryoperation; and communication circuitry to communicate theerror-detection code to a memory controller.
 8. The memory device ofclaim 7, wherein the error-detection code is a cyclic redundancy-check(CRC) code.
 9. The memory device of claim 8, wherein theerror-management circuitry generates the CRC code based on the receivedaddress and data received on at least one data bus.
 10. The memorydevice of claim 1, wherein the address-storage circuitry comprises oneor more latches; and wherein while preventing the memory operation frombeing completed, the error-handling circuitry resets the latches in theaddress-storage circuitry.
 11. The memory device of claim 1, furthercomprising buffer circuitry to buffer data received on at least one databus; wherein the error-handling circuitry discards the data buffered inthe buffer circuitry when the error indication is received.
 12. Thememory device of claim 1, wherein the memory operation is a WRITE orREAD operation.
 13. A method for detecting an address error in a memorysystem, the method comprising: receiving at a memory device an addressfor a memory operation; storing the received address for the memoryoperation; receiving an error indication which indicates an error in thereceived address for the memory operation; and preventing the memoryoperation from being completed in response to the received errorindication.
 14. A memory device, comprising: address-receiving circuitryto receive an address on at least one address bus; data-receivingcircuitry to receive data on at least one data bus; and error-managementcircuitry to generate a CRC code based on the received address and data,wherein the data does not correspond to the memory operation associatedwith the address.
 15. The memory device of claim 14, wherein theerror-management circuitry concatenates the address with the data togenerate the CRC code.
 16. A method for detecting an address error in amemory system, the method comprising: receiving an address on at leastone address bus; receiving data on at least one data bus; and generatinga CRC code based on the received address and data, wherein the data doesnot correspond to the memory operation associated with the address. 17.A memory controller, comprising: address-transmission circuitry totransmit an address for a memory operation; error-detection-codereceiving circuitry to receive an error-detection code corresponding tothe transmitted address; error-detection circuitry to detect an errorbased on the received error-detection code and the transmitted address;and error-indication transmission circuitry to transmit an errorindication, in response to the error-detection circuitry detecting theerror, to prevent the memory operation corresponding to the transmittedaddress from being completed.
 18. The memory controller of claim 17,further comprising a data buffer to buffer data for the memory operationprior to transmitting the address.
 19. The memory controller of claim17, further comprising: an address buffer to buffer the transmittedaddress; and address re-transmission circuitry to re-transmit thebuffered address in response to the error-detection circuitry detectingthe error.
 20. The memory controller of claim 17, wherein the memoryoperation is a WRITE or READ operation.
 21. The memory controller ofclaim 17, wherein the error-detection code is a CRC code based on thetransmitted address.
 22. A method for detecting an address error in amemory system, the method comprising: transmitting an address for amemory operation; receiving an error-detection code corresponding to thetransmitted address; detecting an error based on the receivederror-detection code and transmitted address; transmitting an errorindication, in response to the detected error, to prevent the memoryoperation corresponding to the transmitted address from being completed.23. A memory system, comprising: a memory device; a memory controller;and an address bus which couples the memory device with the memorycontroller; wherein the memory device generates an error-detection codebased on an address transmitted via the address bus and transmits theerror-detection code to the memory controller; wherein the memorycontroller transmits an error indication to the memory device inresponse to the error-detection code; and wherein the error indicationcauses the memory device to discard the received address and prevent amemory operation.
 24. The memory system of claim 23, wherein the memorycontroller comprises a data buffer which buffers the data associatedwith a memory operation corresponding to the transmitted address. 25.The memory system of claim 23, wherein the memory device comprises adata buffer which buffers the data associated with a memory operationcorresponding to the transmitted address.
 26. The memory system of claim23, wherein the memory controller comprises an address buffer whichbuffers the transmitted address and re-transmits the buffered addressafter the error indication is transmitted.
 27. The memory system ofclaim 23, wherein the memory system is a Graphics Double Data Rate,version 5 (GDDR5) memory system.
 28. A memory system, comprising: amemory controller; a memory device; and a signal path coupling thememory controller and the memory device, wherein the signal path carriesan error indication, and wherein the error indication causes the memorydevice to prevent a previously transmitted command from being completed.29. A memory device, comprising: means for receiving an address for amemory operation; means for storing the received address for the memoryoperation; means for receiving an error indication which indicates anerror in the received address for the memory operation; and means forpreventing the memory operation from being completed in response to thereceived error indication.
 30. A memory device, comprising: means forreceiving an address on at least one address bus; means for receivingdata on at least one data bus; and means for generating a CRC code basedon the received address and data, wherein the data does not correspondto the memory operation associated with the address.
 31. A memorycontroller, comprising: means for transmitting an address for a memoryoperation; means for receiving an error-detection code corresponding tothe transmitted address; means for detecting an error based on thereceived error-detection code and the transmitted address; and means fortransmitting an error indication, in response to the error-detectioncircuitry detecting the error, to prevent the memory operationcorresponding to the transmitted address from being completed.